This study examines how formal mathematics can be taught in the Swedish secondary school with its new curriculum for mathematics. The study examines what a teaching material in formal mathematics corresponding to the initial content of the course Mathematics 1c could look like, and whether formal mathematics can be taught to high school students.The survey was conducted with second year students from the science programme. The majority of these students studied the course Mathematics D. The students described themselves as not being motivated towards mathematics.The results show that the content of the curriculum can be presented with formal mathematics. This both in terms of requirements for content and students being able to comprehend this content.

External forces have significant impact on organisations. This study analyzes the implications of one type of external forces in aid-focused NGOs through two qualitative case studies where it is investigated if Sida?s reporting requirements have the intended effects: learning and control using a theoretical framework where it is recognised that the requirements may also result in dysfunctional behaviour: decoupling and colonisation. The study shows that when the demands are the result of institutional pressure rather than an ambition to generate learning and control, the demands tend to be unrealistic and the NGOs therefore decouple the formal fulfilment of the demands from the actual activities. It is argued that a partnership, which incorporates trust and dialogue, is a prerequisite, not only for learning, but also control.

External forces have significant impact on organisations. This study analyzes the implications of one type of external forces in aid-focused NGOs through two qualitative case studies where it is investigated if Sida?s reporting requirements have the intended effects: learning and control using a theoretical framework where it is recognised that the requirements may also result in dysfunctional behaviour: decoupling and colonisation. The study shows that when the demands are the result of institutional pressure rather than an ambition to generate learning and control, the demands tend to be unrealistic and the NGOs therefore decouple the formal fulfilment of the demands from the actual activities. It is argued that a partnership, which incorporates trust and dialogue, is a prerequisite, not only for learning, but also control.

This study examines how formal mathematics can be taught in the Swedishsecondary school with its new curriculum for mathematics. The study examineswhat a teaching material in formal mathematics corresponding to the initialcontent of the course Mathematics 1c could look like, and whether formalmathematics can be taught to high school students.The survey was conducted with second year students from the science programme.The majority of these students studied the course Mathematics D.The students described themselves as not being motivated towards mathematics.The results show that the content of the curriculum can be presented withformal mathematics. This both in terms of requirements for content and studentsbeing able to comprehend this content. The curriculum also requires thatthis type of mathematics is introduced in the course Mathematics 1c.The results also show that students are open towards and want more formalmathematics in their ordinary education. They initially felt it was strangebecause they had never encountered this type of mathematics before, but somestudents found the formal mathematics to be easier than the mathematicsordinarily presented in class.The study finds no reason to postpone the meeting with the formal mathematicsto university level.

According to statistics, requirements management is identified as a major source of error to failed IT-projects. Moreover communication is identified as a factor affecting the require-ments management and can lead to deficiencies in the requirements. The requirements analyst is responsible for managing the requirements from the different stakeholders, act as a com-munication accommodator and to translate abstract requirements expressed by users to more specific requirements that developers can implement. The purpose of this thesis is to study the role of the requirements analyst to investigate the problems that may arise in working with requirements management.  To achieve the purpose we have performed a requirements management process in which we ourselves took the role as the requirements analysts. The requirements management process consisted of three phases: gather requirements, document requirements and validate require-ments.

A paper to analyse how the FAR and SRS associations in Sweden look upon the upcoming changes in the auditbusiness and how this may come to change the Formal requirements when graduating auditors..

This paper is about basic set theory and cardinalities for infinite sets. One of the results are that the line R and the plane R2 contains exactly the same number of points. Because of that the set theory is described with a formal language this the paper has an appendix about formal languages..

The result from Requirements Engineering is a Requirements Specification. Characteristics of a good Requirements Specification are unambiguity, completeness, verifiability, consistency, modifiability, traceability, correctness and ranked for importance and/or stability.This work defines these quality attributes and answers the questions how to reach these attributes and the diffuculties which exist in this area.This work should be read to get an overwiew of the area Requirements Engineering and Requirements Specification..

Background: Learning is important for companies? existence in today?s society and many studies discuss the importance of life long learning and learning organizations. An increased understanding for how the individual learn at the work place is importance to study to gain an accepting for how learning occurs, both formal and informal. Purpose: The purpose with this study is to describe the process of learning at the work place from an individual perspective, with focus on how formal and informal learning occur and interact. The purpose is also to confirm, contradict or develop existing theories.

This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions.A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software.In this paper, both the traditional plan-driven methods and agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented.

The purpose of this Master?s thesis is to examine similarities and differences in qualitative experiences between formal and informal reading groups from the participants? point of view. The empirical data was acquired from interviews with nine reading group participants, of whom four of them participated in formal reading groups and five in informal reading groups. To analyze the empirical data, Louise M. Rosenblatt?s theory concerning reading and a method concerning reading groups by Immi Lundin were used.

Prioritisation of software requirements is a critical part of the development of software. Whichrequirements and in which order they will be developed is one of the main tasks that requirementprioritisation supports.There are different ways that a requirement prioritisation can be used, for example alone or in agroup and with different methods.The purpose of this report is to map out how you can carry out a requirement prioritisation alonewith different types of prioritisation methods and how you solve the problems that can arise whenprioritisting requirements. This is done by documenting the use of three different types of methodsthat can be execute alone. The methods are "100-dollar test", "Ranking" and "Top-tenrequirements".To be able to prioritise requirements, you need to establish which requirements you shall prioritise.The paper retrieves this information by interviewing stakeholders in the system and analysing theresult of the interviews and the execution of the requirement prioritisation.Three problems arose during that work and I present solutions on these problems. The problemswere 1) equivalent requirements when using the "100-dollar test", 2) low differentiation gradebetween the prioritised requirements in the "100-dollar test" and 3) that the requirements that wereprioritised weren't classified before the prioritisation, which leads to inaccuracies in the resultingprioritisation.The solution to the problems that the paper presents is to increase the amount of distributable unitsin the "100-dollar test" to 1000 per requirement, suggestions of classes of the requirements andthe combination of the methods "100-dollar test" and "ranking" to bypass the equivalentrequirements.The report is written in Swedish.Nyckelord: GoTRIS, requirements retrieval, requirements analysis, Viktoria Swedish ICT,requirements prioritisation, requirements, 100-dollar test, ranking, top 10 requirements..

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.